Systems and methods for predicting churn in a multi-tenant system

ABSTRACT

Store a subscription dataset for each tenant of a multi-tenant system, each of the subscription datasets having a common data format native to the system, the subscription datasets including billing data and not behavioral data. Determine primary features from a particular subscription dataset. Derive secondary features from the primary features. Generate a churn prediction model based on the primary features and the secondary features. Obtain a second subscription dataset, the second subscription dataset comprising billing data that is more recent than the particular subscription dataset. Identify, using the particular churn prediction model and the second subscription dataset, one or more subscribers as a churn-risk. Report the one or more subscribers identified as a churn-risk.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication Ser. 62/680,568, filed Jun. 4, 2018, and entitled “Systemand Method for Predicting Churn in a Multi-Tenant System,” which ishereby incorporated by reference herein.

TECHNICAL FIELD

This disclosure pertains to multi-tenant computing systems. Morespecifically, this disclosure pertains to predicting churn in amulti-tenant computing system.

BACKGROUND

Under conventional approaches, predicting churn (that is, predicting thelikelihood a customer may cancel a service) may be determined byreviewing behavioral data. For example, predicting churn analysis may bedetermined by reviewing how often a user accesses the service.Typically, behavioral data is managed by service provider systems andstored in service-provider-managed data warehouse systems that cannot beeasily accessed by external systems. Accordingly, predicting churn intraditional systems would be computationally intensive in terms ofcomputer resources (e.g., memory, bandwidth, processing speeds, and/orthe like) and/or processing time.

SUMMARY

A claimed solution rooted in computer technology overcomes problemsspecifically arising in the realm of computer technology. In variousembodiments, a computing system is configured to predict churn in amulti-tenant system without using behavioral data. This may, forexample, reduce computing resource requirements and/or reduce the amountof processing time to predict churn in a multi-tenant system. Forexample, the multi-tenant system may store billing data in a data format(or, data formats) that is native to the multi-tenant system, and thatdata format may be common across all of the tenants of the multi-tenantsystem. The multi-tenant system may generate churn prediction models foreach of the tenants using their respective billing data. For example,historical billing data for AT&T may be used to generate a churnprediction model for AT&T, and historical billing data for Verizon maybe used to generate a churn prediction model for Verizon. Since thebilling data is local to the multi-tenant system, and in a nativeformat, the multi-tenant system does not need to obtain data innon-native formats from third-party systems, and/or integrate such datainto a data format of the multi-tenant system. The multi-tenant systemmay use the respective churn prediction models to predict churn usingcurrent billing data. For example, the multi-tenant system may identifycurrent AT&T subscribers that are considered a churn-risk (e.g., at riskof canceling their AT&T subscription) using the AT&T churn predictionmodel and the current AT&T billing data, and identify current Verizonsubscribers that are considered a churn-risk using the Verizon churnprediction model and the current Verizon billing data. Since the dataformats are native to the multi-tenant system and common across thetenants, the multi-tenant system may predict churn for any number oftenants of the multi-tenant system without having to integrate largeamounts of external data (e.g., behavioral data). Additionally, billingdatasets are typically much smaller than behavioral datasets, which mayreduce the computing requirements (e.g., memory requirements, processorrequirements) required to predict churn in a multi-tenant system.Furthermore, because the data is in the single native format of themulti-tenant system it is feasible to handle data errors using automatedprograms rather than interventions by system administrators.

Various embodiments of the present disclosure include systems, methods,and non-transitory computer readable media configured to store arespective subscription dataset for each tenant of the multi-tenantsystem, each of the respective subscription datasets having one or morecommon data formats native to the multi-tenant system, wherein therespective subscription datasets include billing data and does notinclude behavioral data. Determine, by a churn prediction engine of themulti-tenant system, one or more primary features from a particularrespective subscription dataset of a particular tenant of themulti-tenant system. Derive, by the churn prediction engine of themulti-tenant system, one or more secondary features from the one or moreprimary features. Generate, by the churn prediction engine of themulti-tenant system, a particular churn prediction model based on theone or more primary features and the one or more secondary features.Obtain, by the churn prediction engine of the multi-tenant system, asecond subscription dataset of the particular tenant of the multi-tenantsystem, the second subscription dataset comprising billing data that ismore recent than the particular respective subscription dataset of theparticular tenant of the multi-tenant system. Identify, by the churnprediction engine of the multi-tenant system using the particular churnprediction model and the second subscription dataset of the particulartenant of the multi-tenant system, one or more subscribers of theparticular tenant of the multi-tenant system as a churn-risk. Report theone or more subscribers of the particular tenant of the multi-tenantsystem identified as a churn-risk.

In some embodiments, the systems, methods, and non-transitory computerreadable media further configured to perform: generating, by the churnprediction engine of the multi-tenant system, a different churnprediction model based on the one or more different primary features andthe one or more different secondary features; obtaining, by the churnprediction engine of the multi-tenant system, a third subscriptiondataset of the different tenant of the multi-tenant system, the thirdsubscription dataset comprising billing data that is more recent thanthe different respective subscription dataset of the different tenant ofthe multi-tenant system; identifying, by the churn prediction engine ofthe multi-tenant system using the different churn prediction model andthe third subscription dataset of the different tenant of themulti-tenant system, one or more different subscribers of the differenttenant of the multi-tenant system as a churn-risk; and reporting the oneor more different subscribers of the different tenant of themulti-tenant system identified as a churn-risk.

In some embodiments, the one or more common data formats native to themulti-tenant system are independent of third-party data formats, and arenot based on an integration of third-party data.

In some embodiments, the churn prediction engine is configured tooperate on the one or more common data formats native to themulti-tenant system, thereby allowing the churn prediction engine to usethe same machine learning algorithm for the particular churn predictionmodel and the different churn prediction model.

In some embodiments, the machine learning algorithm comprises aregression analysis.

In some embodiments, the one or more primary features include date oflast payment and subscription status.

In some embodiments, the one or more second features include length oftime since the date of last payment.

In some embodiments, the one or more second features include any ofmeasures and statistics of plan information keywords.

In some embodiments, the one or more second features include any ofmeasures and statistics of subscription billing amounts.

In some embodiments, the one or more second features include any ofmeasures and statistics of subscription history.

In some embodiments, the one or more second features include any offeatures derived from the use by subscribers of products from differenttenants on the multi-tenants system.

In some embodiments, the particular respective subscription dataset ofthe particular tenant of the multi-tenant system includes a limitednumber of examples of churn.

These and other features of the systems, methods, and non-transitorycomputer readable media disclosed herein, as well as the methods ofoperation and functions of the related elements of structure and thecombination of parts and economies of manufacture, will become moreapparent upon consideration of the following description and theappended claims with reference to the accompanying drawings, all ofwhich form a part of this specification, wherein like reference numeralsdesignate corresponding parts in the various figures. It is to beexpressly understood, however, that the drawings are for purposes ofillustration and description only and are not intended as a definitionof the limits of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a diagram of an example network system for predictingchurn in a multi-tenant system according to some embodiments.

FIG. 2 depicts a diagram of an example churn prediction engine accordingto some embodiments.

FIGS. 3A-B depict a flowchart of an example of a method of predictingchurn in a multi-tenant system according to some embodiments.

FIG. 4 is a diagram of an example computer system for implementing thefeatures disclosed herein according to some embodiments.

DETAILED DESCRIPTION

A claimed solution rooted in computer technology overcomes problemsspecifically arising in the realm of computer technology. In variousembodiments, a computing system is configured to predict churn in amulti-tenant system without using behavioral data. This may, forexample, reduce computing resource requirements and/or reduce the amountof processing time to predict churn in a multi-tenant system. Forexample, the multi-tenant system may store billing data in a data format(or, data formats) that is native to the multi-tenant system, and thatdata format may be common across all of the tenants of the multi-tenantsystem. The multi-tenant system may generate churn prediction models foreach of the tenants using their respective billing data. For example,historical billing data for AT&T may be used to generate a churnprediction model for AT&T, and historical billing data for Verizon maybe used to generate a churn prediction model for Verizon. Since thebilling data is local to the multi-tenant system, and in a nativeformat, the multi-tenant system does not need to obtain data innon-native formats from third-party systems, and/or integrate such datainto a data format of the multi-tenant system. The multi-tenant systemmay use the respective churn prediction models to predict churn usingcurrent billing data. For example, the multi-tenant system may identifycurrent AT&T subscribers that are considered a churn-risk (e.g., at riskof canceling their AT&T subscription) using the AT&T churn predictionmodel and the current AT&T billing data, and identify current Verizonsubscribers that are considered a churn-risk using the Verizon churnprediction model and the current Verizon billing data. Since the dataformats are native to the multi-tenant system and common across thetenants, the multi-tenant system may predict churn for any number oftenants of the multi-tenant system without having to integrate largeamounts of external data (e.g., behavioral data). Additionally, billingdatasets are typically much smaller than behavioral datasets, which mayreduce the computing requirements (e.g., memory requirements, processorrequirements) required to predict churn in a multi-tenant system.Furthermore, because the data is in the single native format of themulti-tenant system it is feasible to handle data errors using automatedprograms rather than interventions by system administrators.

FIG. 1 depicts a diagram of an example network system 100 for predictingchurn in a multi-tenant system 102 according to some embodiments. In theexample of FIG. 1, the network system 100 provides cloud-basedsoftware-as-a-service (SAAS) services of a multi-tenant system 102 tomultiple tenants. Examples of the cloud-based SAAS services include datastorage, data processing, and business-oriented applications. In someembodiments, each tenant may be a subscription-based entity or provider(e.g., an internet service provider, a home security system and serviceprovider, a cellular phone service provider, or entertainment contentprovider). Each tenant may include a group of one or more users (e.g.,individuals, business entities, customers of the business entities,systems) who share access to the cloud-based services. In oneembodiment, a tenant includes a service entity such as AT&T, Netflix,Verizon, and/or the like. A tenant may include one or more products orservices of an entity. For example, AT&T internet products may be aparticular tenant, and AT&T security products may be another tenant. Insome embodiments, the cloud-based SAAS services relate to managingsubscriber records, product and/or service consumption information,billing information, payment information, and/or the like.

The network system 100 includes the multi-tenant system 102 coupled viaa data network 104 (e.g., a set of one or more public and/or private,wired and/or wireless networks) to client devices 106. The multi-tenantsystem 102 includes shared resources to host the cloud-based SAASservices to the tenants. The shared resources may include processors,memory, virtual systems, services, application programs, load balancers,firewalls, and/or the like. As shown, the multi-tenant system 102includes tenant interfaces 110, server systems 112, tenant datastores114, server system datastores 116, and a churn prediction engine 118.Each of the client devices 106 includes a client system 108 thataccesses the cloud-based SAAS services hosted by the multi-tenant system102. In some embodiments, the client systems 108 may be operated byemployees (e.g., administrator users) of the provider of the provider ofthe multi-tenant system 102. In some embodiments, the client systems 108may be operated by employees of the tenant. In some embodiments, theclient systems 108 may be operated by end users of the tenant'sservices.

Each client device 106 may include a desktop, laptop, notebook, tablet,personal digital assistant, smart phone, or other consumer electronicdevices incorporating one or more computer components. The client system108 on each client device 106 may include hardware, software and/orfirmware for communicating with the multi-tenant system 102 andaccessing the cloud-based services it hosts. Examples of the clientsystems 108 may include web browsers, client engines, drivers, userinterface components, proprietary interfaces, and/or the like.

The multi-tenant system 102 includes hardware, software and/or firmwareto host the cloud-based services for the tenants. It will be appreciatedthat the typical multi-tenant system 102 may offer access to sharedresources including systems and applications on shared devices and offereach tenant the same quality or varying qualities of service. In someembodiments, the multi-tenant system 102 does not use virtualization orinstantiation processes. In some embodiments, a multi-tenant system 102integrates several business computing systems into a common system witha view toward streamlining business processes and increasingefficiencies on a business-wide level.

In some embodiments, the multi-tenant system 102 includes a userinterface tier of multiple tenant interfaces 110, a server tier ofmultiple server systems 112, a datastore tier of multiple tenantdatastores 114 for the multiple tenants, one or more system datastores116, and a churn prediction engine 118. In some embodiments, the tenantinterfaces 110 includes graphical user interfaces and/or web-basedinterfaces to enable tenants to access the shared services hosted by themulti-tenant system 102. The tenant interfaces 110 may support loadbalancing when multiple tenants (and/or multiple customers of thetenants) try to access the multi-tenant system 102 concurrently. Thetenant interfaces 110 may additionally or alternatively include anoperator interface for use by a systems operator to configure orotherwise manage the multi-tenant system 102. In some embodiments, eachtenant may be associated with a subset of the total tenant interfaces118 for load balancing.

In some embodiments, the server systems 112 include hardware, softwareand/or firmware to host the shared services for tenants. The hostedservices may include tenant-specific business services or functions,including enterprise resource planning (ERP), customer relationshipmanagement (CRM), eCommerce, Human Resources (HR) management, payroll,financials, accounting, calendaring, order processing, subscriptionbilling, inventory management, supply chain management (SCM),collaboration, sales force automation (SFA), marketing automation,contact list management, call-center support, web-based customersupport, partner and vendor management systems, product lifecyclemanagement (PLM), financial, reporting and analysis, and/or the like.Similar to the tenant interfaces 110, in some embodiments, the serversystems 110 may support load balancing when multiple tenants (and/ormultiple customers of tenants) try to access the multi-tenant system 102concurrently. Further, in some embodiments, each tenant may beassociated with a subset of the total server systems 112 for loadbalancing.

In some embodiments, tenant data 120 for each tenant may be stored in alogical store across one or more tenant datastores 114. In someembodiments, each tenant uses a logical store that is not assigned toany predetermined tenant datastores 114. Each logical store may containtenant data 120 that is used, generated and/or stored as part ofproviding tenant-specific business services or functions. In someembodiments, the tenant datastores 114 may include relational databasemanagement systems (RDBMS), object-based database systems, and/or thelike. In some embodiments, tenant data 120 may be stored across multipletenant datastores 114, with each datastore dedicated to a particularservice (e.g., managing customer records, managing product and/orservice consumption information, managing billing information, managingpayment information, and/or the like).

In some embodiments, the tenant data 120 may include subscriptioninformation, such as billing data and/or subscription status (e.g.,active, canceled, suspended, re-activated). In some embodiments, thetenant data 120 does not include behavioral data. Behavioral data mayinclude user interaction data, such as when a user logs into a service,uses a service, and/or the like. Billing data may include billinginvoice data (e.g., date of invoices and invoice amounts, overage chargedates and overage charge amounts), payment transaction data (e.g., dateof payments, amount of payments), payment methods (e.g., credit card,debit card), payment plan (e.g., annual billing, monthly billing),and/or service plan information (e.g., the name of a service plan).Subscription information may also include a geographic region and/orlocation associated with a tenant, service, and/or subscriber.

In some embodiments, subscription information includes non-behavioralaccount activity (or, simply, account activity), such as newsubscriptions, changes to subscribed products and/or services,cancellation of one or more products and/or services, subscriptions tonew products and/or services, application of discounts, loyalty programpackage changes (e.g., additional programs and/or services, specialrates, and/or the like for loyal customers), reduction or increase ofrates for products and/or services, and/or cancellation of theapplication. In some embodiments, account activity does not includeusage of a product and/or product of a subscriber (e.g., what channelsthe subscriber actually watches, what services and what level ofconsumption the subscriber receives, quality of the product and/orservices, and/or like sub scriber behavioral data).

In some embodiments, the tenant data 120 may be stored in one or moredata formats that are native to the multi-tenant system 102, as definedby one or more data format rules 120. The data format rules 120 may bestored in the system datastore 116, and may define one or more dataformats that are native to the multi-tenant system and/or one or moredata formats that may be used by multiple tenants of the multi-tenantsystem 102 (e.g., each tenant of the multi-tenant system 102). Forexample, the data format rules 120 may define data types, programminglanguages, scripting languages, data value parameters (e.g., dateformats, string lengths), and/or the like, that are native to themulti-tenant system 102. Some or all of the data format rules 120 may beapplied consistently across to the tenants of the multi-tenant system102. Accordingly, the tenant data 120 may be independent of third-partydata formats, and/or may not be based on an integration of third-partydata.

The churn prediction engine 118 may function to predict churn withrespect to tenants and/or products or services of those tenants. Forexample, the churn prediction engine 118 may predict whether asubscriber of a prover's service is at risk for canceling theirsubscription to that service, cancelling an account with the provider,and/or the like. The churn prediction engine 118 can predict churnwithout using behavioral data. For example, the churn prediction engine118 may identify primary features (or, metrics) from the tenant data120, such as the date of a last payment (e.g., Jun. 5, 2018), and thenderive secondary features (or, metrics) based on the primary features.For example, the secondary features may include a length of time sincethe last payment was received (e.g., three months) based on a currentdate (e.g., Sep. 5, 2018) and the date that the last payment wasreceived (e.g., Jun. 5, 2018). The churn prediction engine 118 maygenerate a churn prediction model using the primary and secondaryfeatures. The churn prediction engine 118 may use the churn predictionmodel with current billing data to predict churn for currentsubscribers. Since the tenant data 120 is stored in a native data formatthat is common across tenants of the multi-tenant system 102, the samechurn prediction engine 118 may be used to generate churn predictionmodels and predict churn for the different tenants without requiringlengthy and/or computationally intensive development and/orcustomization of datasets, models, and/or the like.

The data network (or, communication network) 104 may represent one ormore computer networks (e.g., LAN, WAN, or the like) or othertransmission mediums. The data network 104 may provide communicationbetween the systems, engines, datastores, and/or devices describedherein. In some embodiments, the data network 104 includes one or morecomputing devices, routers, cables, buses, and/or other networktopologies (e.g., mesh, and the like). In some embodiments, the datanetwork 104 may be wired and/or wireless. In various embodiments, thedata network 104 may include the Internet, one or more wide areanetworks (WANs) or local area networks (LANs), one or more networks thatmay be public, private, IP-based, non-IP based, and so forth.

FIG. 2 depicts a diagram of an example churn prediction engine 118according to some embodiments. In the example of FIG. 2, the churnprediction engine 118 includes a management engine 202, a primaryfeature generation engine 204, a derivative feature generation engine206, a churn prediction model generation engine 208, a churn analysisengine 210, a reporting engine 212, a presentation engine 214, acommunication engine 216, and a churn prediction engine datastore 218.

The management engine 202 may function to manage (e.g., create, read,update, delete, or otherwise access) subscription information 250,primary features 252, secondary features 254, churn prediction models256, current subscription datasets 258, and/or churn prediction results260. Any of 250-260 may be stored in the churn prediction enginedatastore 218 and/or other datastore(s) associated with the churnprediction engine 118. The management engine 202 may perform any ofthese operations manually (e.g., by a user interacting with a GUI)and/or automatically (e.g., triggered by one or more of the engines204-212). Like other engines described herein, some or all of thefunctionality of the management engine 202 may be included in and/orcooperate with one or more other engines (e.g., engines 204-216).

The primary feature generation engine 204 may function to determineand/or generate primary features 252. For example, the primary featuregeneration engine 204 may generate primary features 252 fromsubscription information 250. Primary features may include billinginvoice data (e.g., date of invoices and invoice amounts, overage chargedates and overage charge amounts), payment transaction data (e.g., dateof payments, amount of payments), payment methods (e.g., credit card,debit card), payment plan (e.g., annual billing, monthly billing),service plan information (e.g., the name of a service plan), and/oraccount or subscription status (e.g., active, canceled). Primaryfeatures may also include a geographic region and/or location associatedwith a tenant, service, and/or subscriber.

In some embodiments, the primary feature generation engine 204 functionsto identify primary features 252 (e.g., plan information) based on akeyword analysis (e.g., as opposed to a unique identifier analysis). Forexample, plans may have overlapping information and/or differentvariants of the plan, and each may have a different unique identifier.In order to capture all of the relevant plans, the primary featuregeneration engine 204 may search the plans for one or more keywords(e.g., “internet service”) and/or may create features based on measuresand/or statistics of the keywords. This may, for example, result inbetter churn prediction accuracy than using the particular planidentifier which may not have as clear a relationship with churn.

The derivative feature generation engine 206 may function to derivesecondary features 254 from one or more primary features 252. Secondaryfeatures 254 may include a length of time since a last payment wasreceived (e.g., three months) based on a current date (e.g., Sep. 5,2018) and a date that the last payment was received (e.g., Jun. 5,2018). Other secondary features may include the total amount paid by asubscriber within a period of time (e.g., the last 90 days), the totalamount of overage charges incurred within a period of time (e.g., thelast 90 days), how much times has passed since the last overage chargewas incurred (e.g., 120 days), and/or the like.

In some embodiments, the secondary features 254 include measures and/orstatistics of subscription billing amounts (e.g., payments, charges,overages, usage fees, and/or the like). In some embodiments, thesecondary features 254 include measures and/or statistics ofsubscription history (e.g., length of time as a subscriber, perviouscancellations on the system, and/or the like). In some embodiments, thesecondary features 254 include features derived from the use bysubscribers of products from different tenants on the multi-tenantssystem 102. For example, the derivative feature generation engine 206may use data relating to an attribute or set of attributes indicatingthat a subscriber(s) uses products from a first tenant (e.g., Verizon)and a second tenant (e.g., AT&T) to predict churn on a product of athird tenant (e.g., Sprint).

In some embodiments, the derivative feature generation engine 206functions to identify secondary features 254 (e.g., plan information)based on a keyword analysis (e.g., as opposed to a unique identifieranalysis). For example, plans may have overlapping information and/ordifferent variants of the plan, and each may have a different uniqueidentifier. In order to capture all of the relevant plans, thederivative feature generation engine 206 may search the plans for one ormore keywords (e.g., “internet service”) and/or may create featuresbased on measures and/or statistics of the keywords. This may, forexample, result in better churn prediction accuracy than using theparticular plan identifier which may not have as clear a relationshipwith churn.

The churn prediction model generation engine 208 may function togenerate churn prediction models 256. For example, the churn predictionmodel 208 may generate churn prediction models 256 using primaryfeatures 252, secondary features 254, and/or subscription information250. The churn prediction models 256 may implement one or more machinelearning techniques, such as regression analysis, bootstrap regressionanalysis, principle component analysis, and/or the like. In someembodiments, the churn prediction model generation engine 208 mayfunction to validate and/or test a churn prediction model 256 usingother datasets (e.g., validations datasets, test datasets). For example,the datasets described herein may include labeled data indicatingwhether data is an example resulting in churn (e.g., positive example),or whether the data is an example that did not result in churn (e.g.,negative example). In various embodiments, the churn prediction model256 described herein may be trained, validated, and/or tested usingdatasets (e.g., subsets of tenant data 120 and/or subscriptioninformation 250) of limited size (e.g., 100 examples of churn).

In some embodiments, the churn prediction model generation engine 208functions to generate churn prediction models 256 based on a sharedchurn prediction model. For example, a shared churn prediction model maybe used by multiple tenants (e.g., AT&T and Verizon) and customized foreach particular tenant (e.g., using their respective data) to generatetheir respective churn prediction models 256. This may, for example,reduce an amount of time required for the churn prediction engine 118 totrain, validate, test, and/or deploy a churn prediction model 256.

In some embodiments, the churn prediction model generation engine 208functions to generate churn prediction models 256 for tenants with notenant data 120 and/or minimal tenant data 120. For example, a tenantmay be new to the multi-tenant system 102, and may not have acquired athreshold number of examples of churn (e.g., 100 examples) to accuratelypredict churn. In some embodiments, the churn prediction modelgeneration engine 208 may generate and/or leverage other datasets, suchas anonymized datasets based on the tenant data 120 of one or moresimilar tenants, plans, and/or the like, to generate churn predictionmodels 256. In some embodiments, template datasets may be used. Forexample, template datasets may represent typical providers (e.g.,internet providers). These other datasets may be used to generate churnprediction models 256 until the tenant has acquired a threshold numberof examples of churn and/or other required amount of information. Forexample, the new tenant may use the other datasets for three-months, andthen transition to their own data.

In some embodiments, the other datasets may be blended with their tenantdata 120. For example, at one or more threshold levels of examples ofchurn (e.g., 30 examples, 50 example, 80 examples), the churn predictionmodel generation engine 208 may reduce the amount of data used from theother datasets, and increase the amount of their own tenant data 120used to generate the churn prediction model 256. Like the churnprediction model generation engine 208, the primary feature generationengine 204 and/or the derivative feature generation engine 206 maygenerate features based on the other datasets if the tenant has notacquired sufficient tenant data 120.

The churn analysis engine 210 may function to predict churn in themulti-tenant system 102. The churn analysis engine 210 may identify oneor more subscribers and/or plans that are considered to be a churn-riskusing a churn prediction model 256 and a current subscription dataset258 as input values for the churn prediction model 256. In someembodiments, a churn-risk may be a subscriber that has a likelihood ofchurn that exceeds a threshold. For example, if a subscriber has greaterthan an 50% likelihood of churn, then the churn analysis engine 210 mayindicate the subscriber as a churn-risk. The current subscriptiondataset 258 may be a subset of the tenant data 120, and may include morerecent data than the tenant data 120 used to generate the churnprediction model 256. For example, a first subset of the tenant data 120may be used to generate the features 252 and 254, and a second subset ofthe tenant data 120 may be used to predict churn in the multi-tenantsystem 102.

The reporting engine 212 may function to generate reports 260 indicatingchurn prediction results. For example, the reporting engine 212 maygenerate reports 260 indicating subscribers and/or plans that arepredicted to be a churn risk by the churn analysis engine 210, thelikelihood that the particular subscribers will churn, and/or the like.Reports may include subscriber information, plan information, and/or thelike. The reporting engine 212 may configure the reports 212 forpresentation in a graphical user interface.

The presentation engine 214 may function to generate, present and/ordisplay one or more dashboards and/or graphical user interfaces. Forexample, a dashboard may allow a user (e.g., a tenant administrator) toview reports 260, request a churn prediction and/or reports 260, viewtenant data 120, and/or the like. The presentation engine 214 maycooperate with one or more other systems to provide such interfaces. Forexample, the presentation engine 214 may generate server-side portionsof the interfaces, and client systems 108 may generate client-sideportions of the interfaces.

In some embodiments, the presentation engine 214 functions to presentinterfaces allowing users (e.g., tenant administrators) to interact withone or more of the other engines of the churn prediction engine 118. Insome embodiments, the presentation engine 214 functions to presentinterfaces allowing users to perform remedial actions in response tochurn prediction results. For example, a report 260 may indicate JohnSmith is a churn-risk, at which point the user may offer John Smithincentives, discounts, and/or the like, in order to reduce a likelihoodthat John Smith cancels his subscription and/or otherwise churns. Inanother example, a report 260 may indicate that a particular plan isassociated with high subscriber churn (e.g., greater than a thresholdamount). A user may modify that plan, and/or suggest other plans, inorder to reduce the amount of churn associated with that particularplan.

The communication engine 218 may function to send requests, transmitand, receive communications, and/or otherwise provide communication withone or a plurality of the systems, engines, and/or datastores describedherein. In some embodiments, the communication engine 218 functions toencrypt and decrypt communications. The communication engine 218 mayfunction to send requests to and receive data from one or more systemsthrough a network or a portion of a network. Depending uponimplementation-specific considerations, the communication engine 218 maysend requests and receive data through a connection, all or a portion ofwhich may be a wireless connection. The communication engine 218 mayrequest and receive messages, and/or other communications fromassociated systems and/or engines. Communications may be stored in thechurn prediction engine datastore 218.

FIGS. 3A-B depict a flowchart of an example of a method 300 ofpredicting churn in a multi-tenant system according to some embodiments.In this and other flowcharts and/or sequence diagrams, the flowchartillustrates by way of example a sequence of steps. It should beunderstood the steps may be reorganized for parallel execution, orreordered, as applicable. Moreover, some steps that could have beenincluded may have been removed to avoid providing too much informationfor the sake of clarity and some steps that were included could beremoved, but may have been included for the sake of illustrativeclarity.

In step 302, a multi-tenant system (e.g., multi-tenant system 102)stores a respective subscription dataset (e.g., tenant data 120 and/orsubscription information 250) for each tenant of the multi-tenantsystem. Each of the respective subscription datasets may have one ormore common data formats (e.g., as defined by data format rules 122)native to the multi-tenant system. The respective subscription datasetsinclude billing data without including behavioral data. In someembodiments, the multi-tenant system stores the respective subscriptiondatasets in a datastore (e.g., tenant datastore 114 and/or churnprediction engine datastore 218).

In some embodiments, the one or more common data formats native to themulti-tenant system are independent of third-party data formats, and/orare not based on an integration of third-party data. In someembodiments, the particular respective subscription dataset of theparticular tenant of the multi-tenant system includes a limited numberof examples of churn.

In step 304, the multi-tenant system determines, by a churn predictionengine (e.g., churn prediction engine 118) of the multi-tenant system,one or more primary features (e.g., primary features 252) from aparticular respective subscription dataset of a particular tenant (e.g.,AT&T) of the multi-tenant system. For example, the one or more primaryfeatures include date of last payment and a subscription status (e.g.,active, canceled). In some embodiments, a primary feature generationengine (e.g., primary feature generation engine 204) determines the oneor more primary features.

In step 306, the multi-tenant system derives, by the churn predictionengine of the multi-tenant system, one or more secondary features (e.g.,secondary features 254) from the one or more primary features. Forexample, the one or more second features include length of time sincethe date of last payment. In some embodiments, a derivative featuregeneration engine (e.g., derivative feature generation engine 206)determines the one or more secondary features.

In step 308, the multi-tenant system generates, by the churn predictionengine of the multi-tenant system, a particular churn prediction model(e.g., a churn prediction model 256) based on the one or more primaryfeatures and the one or more secondary features. The particular churnprediction model may be based on a shared churn prediction model. Forexample, a shared churn prediction model may be used by multiple tenants(e.g., AT&T and Verizon) and customized for each particular tenant(e.g., using their respective data). In some embodiments, a churnprediction model generation engine (e.g., churn prediction modelgeneration engine 208) generates the particular churn prediction model.

In step 310, the multi-tenant system obtains, by the churn predictionengine of the multi-tenant system, a second subscription dataset (e.g.,current subscription dataset 258) of the particular tenant of themulti-tenant system. The second subscription dataset may comprisebilling data that is more recent than the particular respectivesubscription dataset of the particular tenant of the multi-tenantsystem. In some embodiments, a management engine (e.g., managementengine 202) obtains the second subscription dataset from a datastore(e.g., churn prediction engine datastore 218).

In step 312, the multi-tenant system identifies, by the churn predictionengine of the multi-tenant system using the particular churn predictionmodel and the second subscription dataset of the particular tenant ofthe multi-tenant system, one or more subscribers of the particulartenant of the multi-tenant system as a churn-risk. For example, thesecond subscription dataset may be used as input for the churnprediction model. In some embodiments, a churn analysis engine (e.g.,churn analysis engine 210) identifies the one or more subscribers as achurn-risk.

In step 314, the multi-tenant system reports the one or more subscribersof the particular tenant of the multi-tenant system identified as achurn-risk. In some embodiments, a reporting engine (e.g., reportingengine 212) may generate a report (e.g., churn prediction report 260)indicating the identified one or more subscribers. In some embodiments,a presentation engine (e.g., presentation engine 214) may generate oneor more graphical user interfaces, and/or portions thereof (e.g.,server-side portions), for graphically presenting the report.

In step 316, the multi-tenant system determines, by the churn predictionengine of the multi-tenant system, one or more different primaryfeatures (e.g., different primary features 252) from a differentrespective subscription dataset (e.g., different tenant data 120 and/ordifferent subscription information 250) of a different tenant (e.g.,Verizon) of the multi-tenant system. As used here, the different primaryfeatures may be “different” from the primary features determined in step304, and the different respective subscription dataset may be“different” from the particular respective subscription dataset recitedin the step 304. In some embodiments, the primary feature generationengine determines the one or more different primary features.

In step 318, the multi-tenant system derives, by the churn predictionengine of the multi-tenant system, one or more different secondaryfeatures (e.g., different secondary features 254) from the one or moredifferent primary features. As used here, the different secondaryfeatures may be “different” from the secondary features derived in step306. In some embodiments, the derivative feature generation enginederives the one or more different secondary features.

In step 320, the multi-tenant system generates, by the churn predictionengine of the multi-tenant system, a different churn prediction model(e.g., a different churn prediction model 256) based on the one or moredifferent primary features and the one or more different secondaryfeatures. As used here, the different churn prediction model may be“different” from the churn prediction model generated in step 308. Insome embodiments, the churn prediction model generation engine generatesthe different churn prediction model.

In step 322, the multi-tenant system obtains, by the churn predictionengine of the multi-tenant system, a third subscription dataset (e.g.,another current subscription dataset 258) of the different tenant of themulti-tenant system. The third subscription dataset may comprise billingdata that is more recent than the different respective subscriptiondataset of the different tenant of the multi-tenant system. In someembodiments, the management engine obtains the third subscriptiondataset from the datastore.

In step 324, the multi-tenant system identifies, by the churn predictionengine of the multi-tenant system using the different churn predictionmodel and the third subscription dataset of the different tenant of themulti-tenant system, one or more different subscribers of the differenttenant of the multi-tenant system as a churn-risk. For example, thethird subscription dataset may be used as input for the different churnprediction model. As used here, the different subscribers may be“different” from the subscribers identified in step 312. In someembodiments, the churn analysis engine identifies the one or moredifferent subscribers of the different tenant of the multi-tenant systemas a churn-risk

In step 326, the multi-tenant system reports the one or more differentsubscribers of the different tenant of the multi-tenant systemidentified as a churn-risk. In some embodiments, the reporting enginemay generate another report (e.g., another churn prediction report 260)indicating the identified one or more different subscribers. In someembodiments, the presentation engine (may generate one or more graphicaluser interfaces, and/or portions thereof (e.g., server-side portions),for graphically presenting the report.

In some embodiments, the churn prediction engine is configured tooperate on the one or more common data formats native to themulti-tenant system, thereby allowing the churn prediction engine to usethe same machine learning algorithm for the particular churn predictionmodel and the different churn prediction model. In some embodiments, themachine learning algorithm comprises a regression analysis.

FIG. 4 depicts a diagram 400 of an example of a computing device 402.Any of the systems, engines, datastores, and/or networks describedherein may comprise an instance of one or more computing devices 402. Insome embodiments, functionality of the computing device 402 is improvedto the perform some or all of the functionality described herein. Thecomputing device 402 comprises a processor 404, memory 406, storage 408,an input device 410, a communication network interface 412, and anoutput device 414 communicatively coupled to a communication channel416. The processor 404 is configured to execute executable instructions(e.g., programs). In some embodiments, the processor 404 comprisescircuitry or any processor capable of processing the executableinstructions.

The memory 406 stores data. Some examples of memory 406 include storagedevices, such as RAM, ROM, RAM cache, virtual memory, and/or the like.In various embodiments, working data is stored within the memory 406.The data within the memory 406 may be cleared or ultimately transferredto the storage 408.

The storage 408 includes any storage configured to retrieve and storedata. Some examples of the storage 408 include flash drives, harddrives, optical drives, cloud storage, and/or magnetic tape. Each of thememory system 406 and the storage system 408 comprises acomputer-readable medium, which stores instructions or programsexecutable by processor 404.

The input device 410 is any device that inputs data (e.g., mouse andkeyboard). The output device 414 outputs data (e.g., a speaker ordisplay). It will be appreciated that the storage 408, input device 410,and output device 414 may be optional. For example, therouters/switchers may comprise the processor 404 and memory 406 as wellas a device to receive and output data (e.g., the communication networkinterface 412 and/or the output device 414).

The communication network interface 412 may be coupled to a network(e.g., network 108) via the link 418. The communication networkinterface 412 may support communication over an Ethernet connection, aserial connection, a parallel connection, and/or an ATA connection. Thecommunication network interface 412 may also support wirelesscommunication (e.g., 802.11 a/b/g/n, WiMax, LTE, WiFi). It will beapparent that the communication network interface 412 may support manywired and wireless standards.

It will be appreciated that the hardware elements of the computingdevice 402 are not limited to those depicted in FIG. 4. A computingdevice 402 may comprise more or less hardware, software and/or firmwarecomponents than those depicted (e.g., drivers, operating systems, touchscreens, biometric analyzers, and/or the like). Further, hardwareelements may share functionality and still be within various embodimentsdescribed herein. In one example, encoding and/or decoding may beperformed by the processor 404 and/or a co-processor located on a GPU(i.e., NVidia).

It will be appreciated that an “engine,” “system,” “datastore,” and/or“database” may comprise software, hardware, firmware, and/or circuitry.In one example, one or more software programs comprising instructionscapable of being executable by a processor may perform one or more ofthe functions of the engines, datastores, databases, or systemsdescribed herein. In another example, circuitry may perform the same orsimilar functions. Alternative embodiments may comprise more, less, orfunctionally equivalent engines, systems, datastores, or databases, andstill be within the scope of present embodiments. For example, thefunctionality of the various systems, engines, datastores, and/ordatabases may be combined or divided differently. The datastore ordatabase may include cloud storage. It will further be appreciated thatthe term “or,” as used herein, may be construed in either an inclusiveor exclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance.

The datastores described herein may be any suitable structure (e.g., anactive database, a relational database, a self-referential database, atable, a matrix, an array, a flat file, a documented-oriented storagesystem, a non-relational No-SQL system, and the like), and may becloud-based or otherwise.

The systems, methods, engines, datastores, and/or databases describedherein may be at least partially processor-implemented, with aparticular processor or processors being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors or processor-implemented engines. Moreover, theone or more processors may also operate to support performance of therelevant operations in a “cloud computing” environment or as a “softwareas a service” (SaaS). For example, at least some of the operations maybe performed by a group of computers (as examples of machines includingprocessors), with these operations being accessible via a network (e.g.,the Internet) and via one or more appropriate interfaces (e.g., anApplication Program Interface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example embodiments, the processorsor processor-implemented engines may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented engines may be distributed across a number ofgeographic locations.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

The present invention(s) are described above with reference to exampleembodiments. It will be apparent to those skilled in the art thatvarious modifications may be made and other embodiments may be usedwithout departing from the broader scope of the present invention(s).Therefore, these and other variations upon the example embodiments areintended to be covered by the present invention(s).

1. A multi-tenant system comprising: one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the multi-tenant system to perform: storing a respectivesubscription dataset for each tenant of the multi-tenant system, each ofthe respective subscription datasets having one or more common dataformats native to the multi-tenant system, wherein the respectivesubscription datasets include billing data and does not includebehavioral data; determining, by a churn prediction engine of themulti-tenant system, one or more primary features from a particularrespective subscription dataset of a particular tenant of themulti-tenant system; deriving, by the churn prediction engine of themulti-tenant system, one or more secondary features from the one or moreprimary features; generating, by the churn prediction engine of themulti-tenant system, a particular churn prediction model based on theone or more primary features and the one or more secondary features;obtaining, by the churn prediction engine of the multi-tenant system, asecond subscription dataset of the particular tenant of the multi-tenantsystem, the second subscription dataset comprising billing data that ismore recent than the particular respective subscription dataset of theparticular tenant of the multi-tenant system; identifying, by the churnprediction engine of the multi-tenant system using the particular churnprediction model and the second subscription dataset of the particulartenant of the multi-tenant system, one or more subscribers of theparticular tenant of the multi-tenant system as a churn-risk; andreporting the one or more subscribers of the particular tenant of themulti-tenant system identified as a churn-risk.
 2. The multi-tenantsystem of claim 1, wherein the instructions further cause themulti-tenant to perform: determining, by the churn prediction engine ofthe multi-tenant system, one or more different primary features from adifferent respective subscription dataset of a different tenant of themulti-tenant system; deriving, by the churn prediction engine of themulti-tenant system, one or more different secondary features from theone or more different primary features; generating, by the churnprediction engine of the multi-tenant system, a different churnprediction model based on the one or more different primary features andthe one or more different secondary features; obtaining, by the churnprediction engine of the multi-tenant system, a third subscriptiondataset of the different tenant of the multi-tenant system, the thirdsubscription dataset comprising billing data that is more recent thanthe different respective subscription dataset of the different tenant ofthe multi-tenant system; identifying, by the churn prediction engine ofthe multi-tenant system using the different churn prediction model andthe third subscription dataset of the different tenant of themulti-tenant system, one or more different subscribers of the differenttenant of the multi-tenant system as a churn-risk; and reporting the oneor more different subscribers of the different tenant of themulti-tenant system identified as a churn-risk.
 3. The multi-tenantsystem of claim 2, wherein the one or more common data formats native tothe multi-tenant system are independent of third-party data formats, andare not based on an integration of third-party data.
 4. The multi-tenantsystem of claim 3, wherein the churn prediction engine is configured tooperate on the one or more common data formats native to themulti-tenant system, thereby allowing the churn prediction engine to usethe same machine learning algorithm for the particular churn predictionmodel and the different churn prediction model.
 5. The multi-tenantsystem of claim 4, wherein the machine learning algorithm comprises aregression analysis.
 6. The multi-tenant system of claim 1, wherein theone or more primary features include date of last and subscriptionstatus.
 7. The multi-tenant system of claim 6, wherein the one or moresecond features include length of time since the date of last payment.8. The multi-tenant system of claim 6, wherein the one or more secondfeatures include any of measures and statistics of plan informationkeywords.
 9. The multi-tenant system of claim 6, wherein the one or moresecond features include any of measures and statistics of subscriptionbilling amounts.
 10. The multi-tenant system of claim 6, wherein the oneor more second features include any of measures and statistics ofsubscription history.
 11. The multi-tenant system of claim 6, whereinthe one or more second features include any of features derived from theuse by subscribers of products from different tenants on themulti-tenants system.
 12. The multi-tenant system of claim 1, whereinthe particular respective subscription dataset of the particular tenantof the multi-tenant system includes a limited number of examples ofchurn.
 13. A method being implemented by a computing system includingone or more physical processors and storage media storingmachine-readable instructions, the method comprising: storing arespective subscription dataset for each tenant of the multi-tenantsystem, each of the respective subscription datasets having one or morecommon data formats native to the multi-tenant system, wherein therespective subscription datasets include billing data and does notinclude behavioral data; determining, by a churn prediction engine ofthe multi-tenant system, one or more primary features from a particularrespective subscription dataset of a particular tenant of themulti-tenant system; deriving, by the churn prediction engine of themulti-tenant system, one or more secondary features from the one or moreprimary features; generating, by the churn prediction engine of themulti-tenant system, a particular churn prediction model based on theone or more primary features and the one or more secondary features;obtaining, by the churn prediction engine of the multi-tenant system, asecond subscription dataset of the particular tenant of the multi-tenantsystem, the second subscription dataset comprising billing data that ismore recent than the particular respective subscription dataset of theparticular tenant of the multi-tenant system; identifying, by the churnprediction engine of the multi-tenant system using the particular churnprediction model and the second subscription dataset of the particulartenant of the multi-tenant system, one or more subscribers of theparticular tenant of the multi-tenant system as a churn-risk; andreporting the one or more subscribers of the particular tenant of themulti-tenant system identified as a churn-risk.
 14. The method of claim13, further comprising: determining, by the churn prediction engine ofthe multi-tenant system, one or more different primary features from adifferent respective subscription dataset of a different tenant of themulti-tenant system; deriving, by the churn prediction engine of themulti-tenant system, one or more different secondary features from theone or more different primary features; generating, by the churnprediction engine of the multi-tenant system, a different churnprediction model based on the one or more different primary features andthe one or more different secondary features; obtaining, by the churnprediction engine of the multi-tenant system, a third subscriptiondataset of the different tenant of the multi-tenant system, the thirdsubscription dataset comprising billing data that is more recent thanthe different respective subscription dataset of the different tenant ofthe multi-tenant system; identifying, by the churn prediction engine ofthe multi-tenant system using the different churn prediction model andthe third subscription dataset of the different tenant of themulti-tenant system, one or more different subscribers of the differenttenant of the multi-tenant system as a churn-risk; and reporting the oneor more different subscribers of the different tenant of themulti-tenant system identified as a churn-risk.
 15. The method of claim14, wherein the one or more common data formats native to themulti-tenant system are independent of third-party data formats, and arenot based on an integration of third-party data.
 16. The method of claim15, wherein the churn prediction engine is configured to operate on theone or more common data formats native to the multi-tenant system,thereby allowing the churn prediction engine to use the same machinelearning algorithm for the particular churn prediction model and thedifferent churn prediction model.
 17. The method of claim 16, whereinthe machine learning algorithm comprises a regression analysis.
 18. Themethod of claim 13, wherein the one or more primary features includedate of last and subscription status.
 19. The method of claim 18,wherein the one or more second features include length of time since thedate of last payment.
 20. A non-transitory computer readable mediumcomprising instructions that, when executed, cause one or moreprocessors to perform: storing a respective subscription dataset foreach tenant of the multi-tenant system, each of the respectivesubscription datasets having one or more common data formats native tothe multi-tenant system, wherein the respective subscription datasetsinclude billing data and does not include behavioral data; determining,by a churn prediction engine of the multi-tenant system, one or moreprimary features from a particular respective subscription dataset of aparticular tenant of the multi-tenant system; deriving, by the churnprediction engine of the multi-tenant system, one or more secondaryfeatures from the one or more primary features; generating, by the churnprediction engine of the multi-tenant system, a particular churnprediction model based on the one or more primary features and the oneor more secondary features; obtaining, by the churn prediction engine ofthe multi-tenant system, a second subscription dataset of the particulartenant of the multi-tenant system, the second subscription datasetcomprising billing data that is more recent than the particularrespective subscription dataset of the particular tenant of themulti-tenant system; identifying, by the churn prediction engine of themulti-tenant system using the particular churn prediction model and thesecond subscription dataset of the particular tenant of the multi-tenantsystem, one or more subscribers of the particular tenant of themulti-tenant system as a churn-risk; and reporting the one or moresubscribers of the particular tenant of the multi-tenant systemidentified as a churn-risk.